Management Of Corporate Entities

ABSTRACT

Systems and methods are provided to facilitate corporate entity management. According to some embodiments, a user interface is provided including an entity selection area allowing selection of at least one corporate entity from a plurality of corporate entities, and a plurality of selectable elements, each of the selectable elements being selectable to cause presentation of an associated area, wherein an area associated with each of the plurality of selectable elements presents information relating to the at least one corporate entity and to the associated selectable element.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority to Provisional Application Ser. No.60/401,285, filed Aug. 6, 2002 and entitled “Management of CorporateEntities”.

FIELD

The present invention relates to the management of corporate entities.In particular, the present invention relates to efficient management ofinformation relating to a plurality of interrelated and/or unrelatedcorporate entities.

BACKGROUND

Modern business transactions commonly involve several corporateentities. In a typical transaction, each involved corporate entity maybe owned by several shareholders, one or more of which may be another ofthe involved entities. The entities may also have different corporatestructures, reporting requirements and applicable laws that should beappropriately dealt with during the transaction. In order to preparetransaction documents and execute procedures that address each of theseconcerns, entity representatives are often required to track and manageofficers, documents and other specific characteristics associated witheach entity.

Specific characteristics of corporate entities come into play evenoutside the context of a particular transaction. In this regard,corporate “housekeeping” required by laws applicable to a particularentity includes activities such as electing officers, complying with taxand regulatory filing deadlines, and holding board meetings. Again,these activities require tracking of a myriad of details for eachcorporate entity.

Recently, computer databases have been employed to track informationassociated with corporate entities. According to these systems,tax-related information is tracked and accessed by an accountingdepartment, while corporate structure information is tracked andaccessed by a corporate department. Oftentimes the systems employed byeach department are incompatible, thereby inhibiting transfer ofinformation among departments. Even if information associated withseveral corporate entities were available in a centrally-accessible datadepository, current systems are unable to present the data in a mannerthat facilitates efficient tracking, editing and/or use thereof.

In view of the foregoing, what is needed are improvements in themanagement of information associated with corporate entities. Suchimprovements may in turn enable efficient management of the associatedcorporate entities.

SUMMARY

To address the foregoing, embodiments of the present invention concern asystem, a method, an apparatus, a computer-readable medium storingprocessor-executable process steps, and means to present a plurality ofselectable elements and an entity selection area, the entity selectionarea allowing selection of at least one corporate entity from aplurality of corporate entities, receive a selection of the at least onecorporate entity, receive a selection of one of the plurality ofselectable elements, determine information associated with the at leastone corporate entity and the one selected element, and present thedetermined information to a user.

Embodiments of the present invention also provide a user interface whichincludes interface an entity selection area allowing selection of atleast one corporate entity from a plurality of corporate entities, and aplurality of selectable elements, each of the selectable elements beingselectable to cause presentation of an associated area, wherein an areaassociated with each of the plurality of selectable elements presentsinformation relating to the at least one corporate entity and to theassociated selectable element.

With these and other advantages and features of the invention that willbecome hereinafter apparent, the invention may be more clearlyunderstood by reference to the following detailed description of theinvention, the appended claims, and the drawings attached hereto.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a topographic view of a network architecture according to someembodiments of the present invention.

FIG. 2 is a block diagram of an internal architecture of an entitymanagement server according to some embodiments to the presentinvention.

FIG. 3 is a block diagram of an internal architecture of a corporateentity server according to some embodiments to the present invention.

FIG. 4 is a block diagram of an internal architecture of a user deviceaccording to some embodiments to the present invention.

FIG. 5 is a representative view of a tabular portion of an entityrelationship database according to some embodiments of the presentinvention.

FIG. 6 is a representative view of a tabular portion of a generalinformation database according to some embodiments of the presentinvention.

FIG. 7 is a representative view of a tabular portion of a legal databaseaccording to some embodiments of the present invention.

FIG. 8 is a representative view of a tabular portion of a contactsdatabase according to some embodiments of the present invention.

FIG. 9 is a representative view of a tabular portion of an ownersdatabase according to some embodiments of the present invention.

FIG. 10 is a representative view of a tabular portion of a regulatorsdatabase according to some embodiments of the present invention.

FIG. 11 is a representative view of a tabular portion of an officersdatabase according to some embodiments of the present invention.

FIG. 12 is a representative view of a tabular portion of a jurisdictionsdatabase according to some embodiments of the present invention.

FIG. 13 is a representative view of a tabular portion of a reportingdatabase according to some embodiments of the present invention.

FIG. 14 is a representative view of a tabular portion of a controllersdatabase according to some embodiments of the present invention.

FIG. 15 is a representative view of a tabular portion of a fundsdatabase according to some embodiments of the present invention.

FIG. 16 is a representative view of a tabular portion of a documentgeneration database according to some embodiments of the presentinvention.

FIG. 17 is a representative view of an interface according to someembodiments of the present invention.

FIG. 18 is a representative view of an interface according to someembodiments of the present invention.

FIG. 19 is a representative view of an interface according to someembodiments of the present invention.

FIG. 20 is a representative view of an interface according to someembodiments of the present invention.

FIG. 21 is a representative view of an interface according to someembodiments of the present invention.

FIG. 22 is a representative view of an interface according to someembodiments of the present invention.

FIG. 23 is a representative view of an interface according to someembodiments of the present invention.

FIG. 24 is a representative view of an interface according to someembodiments of the present invention.

FIG. 25 is a representative view of an interface according to someembodiments of the present invention.

FIG. 26 is a representative view of an interface according to someembodiments of the present invention.

FIG. 27 is a representative view of an interface according to someembodiments of the present invention.

FIG. 28 is a representative view of an interface according to someembodiments of the present invention.

FIG. 29 is a representative view of an interface according to someembodiments of the present invention.

FIG. 30 is a representative view of an interface according to someembodiments of the present invention.

DETAILED DESCRIPTION

System Architecture

FIG. 1 illustrates a network architecture of a system according to someembodiments of the present invention. As shown, communication network100 provides communication between entity management server 200, entityservers 300, 310 and 320, and user devices 400 and 410.

Communication network 100 may comprise any number of different systemsfor transferring data, including a Local Area Network (LAN), aMetropolitan Area Network (MAN), a Wide Area Network (WAN), aproprietary network, a Public Switched Telephone Network (PSTN), aWireless Application Protocol (WAP) network, a wireless LAN (e.g., inaccordance with the Institute of Electrical and Electronics Engineers802.11 standard), a Bluetooth network, an Infrared Radiation (IR)network, and/or an IP network such as the Internet, an intranet or anextranet. As used herein, the term “communication” can refer to wiredand/or wireless communication as appropriate.

Entity management server 200 is used to provide an interface tofacilitate the management of corporate entities in accordance with someembodiments of the invention. As will be described in detail below, suchan interface may be provided through presentation of a plurality ofselectable elements and an entity selection area, the entity selectionarea allowing selection of at least one corporate entity from aplurality of corporate entities, receive a selection of the at least onecorporate entity, reception of a selection of one of the plurality ofselectable elements, determination of information associated with the atleast one corporate entity and the one selected element, andpresentation of the determined information to a user.

In one specific example, entity management server 200 receivesinformation associated with corporate entities from many differentsources such as entity servers 300, 310 and 320 and stores theinformation in appropriate databases of server 200. Entity managementserver 200 then receives a request for information from one of userdevices 400 and 410. The requested information is retrieved from thedatabases of entity management server 200 and used to create aninterface according to some embodiments of the invention. The interfaceis presented to the user device from which the request was received, andthe user device in turn presents the interface to a user. This and otherspecific examples are discussed in more detail below.

Entity management server 200 is depicted as a mainframe server in FIG.1, but may comprise any device or devices capable of performing processsteps attributed to server 200 herein. Moreover, entity managementserver 200 may provide entity management services to more than onemanaging entities. Other services may also be provided by entitymanagement server 200, including functions usable by disparatecompanies, departments, and/or offices. In this regard, entitymanagement server 200 may be operated by a company in order to managecorporate entities related to the company, or by a company providingthis management as an outsourced function.

Entity servers 300, 310 and 320 store information relating to corporateentities. Each of servers 300, 310 and 320 may store informationrelating to a single respective entity, and one or more of servers 300,310 and 320 may store information relating to two or more entities. Inthe former case, entity servers 300, 310 and 320 may comprise centraldata repositories maintained by their respective entities. Theinformation stored in entity servers 300, 310 and 320 may therefore begenerated by business activities of the respective entities. Theinformation may also be input by an operator having authorization toinput information. As shown, entity server 300 also functions as anetwork server for serving applications and data to terminals 302through 308.

User devices 400 and 410 comprise a personal computer and a personaldigital assistant, respectively. User devices 400 and 410 are capable ofcommunicating with entity management server 200 over communicationnetwork 100, and of presenting an interface to a user in operationthereof. In some embodiments, such an interface includes an entityselection area allowing selection of at least one corporate entity froma plurality of corporate entities, and a plurality of selectableelements, each of the selectable elements being selectable to causepresentation of an associated area, wherein an area associated with eachof the plurality of selectable elements presents information relating tothe at least one corporate entity and to the associated selectableelement.

In other embodiments, the devices of FIG. 1 are connected differentlythan as shown. For example, some or all of the devices may be connecteddirectly to one another. Of course, embodiments of the invention mayinclude devices that are different from those shown. It should also benoted that although the devices are shown in communication with eachother, the devices need not be constantly exchanging data. Rather,communication may be established when necessary and severed at othertimes or always available but rarely used to transmit data. Moreover,although the illustrated communication links appear dedicated, it shouldbe noted that each of the links may be shared by other devices.

Entity Management Server

FIG. 2 is a block diagram of an internal architecture of entitymanagement server 200 according to some embodiments of the invention. Asillustrated, entity management server 200 includes microprocessors 210in communication with communication bus 220. Microprocessors 210 maycomprise RISC-based and other types of processors and are used toexecute processor-executable process steps so as to control the elementsof entity management server 200 to provide desired functionality.

Also in communication with communication bus 220 is communication port230. Communication port 230 is used to transmit data to and to receivedata from devices external to entity management server 200 such asdevices 300 through 510. Communication port 230 is therefore preferablyconfigured with hardware suitable to physically interface with desiredexternal devices and/or network connections. For example, communicationport 230 may comprise an Ethernet connection to a local area networkthrough which entity management server 200 may receive and transmitinformation over the Web.

Input device 240, display 250 and printer 260 are also in communicationwith communication bus 220. Any known input device may comprise inputdevice 240, including a keyboard, mouse, touch pad, voice-recognitionsystem, or any combination of these devices. Of course, information mayalso be input to entity management server 200 from other devices viacommunication port 230. Display 250 may be an integral or separate CRTdisplay, flat-panel display or the like used to display graphics andtext in response to commands issued by microprocessors 210. Printer 260may also present text and graphics to an operator, but in hardcopy formusing ink-jet, thermal, dot-matrix, laser, or other printingtechnologies. Elements 240 through 260 are most likely used sparinglyduring operation of entity management server 200, but may be used by anoperator for setup and administration.

RAM 265 is connected to communication bus 220 to provide microprocessors210 with fast data storage and retrieval. In this regard,processor-executable process steps being executed by microprocessors 210are typically stored temporarily in RAM 265 and executed therefrom bymicroprocessors 210. ROM 270, in contrast, provides storage from whichdata can be retrieved but to which data cannot be stored. Accordingly,ROM 270 is used to store invariant process steps and other data, such asbasic input/output instructions and data used during boot-up of entitymanagement server 200 or to control communication port 230. It should benoted that one or both of RAM 265 and ROM 270 may communicate directlywith microprocessors 210 instead of over communication bus 220.

Data storage device 280 stores, among other data, processor-executableprocess steps of entity management application 281. Microprocessors 210therefore execute the process steps of entity management application 281in order to control entity management server 200 to facilitate corporateentity management according to some embodiments of the presentinvention.

The process steps of entity management application 281 may be read froma computer-readable medium, such as a floppy disk, a CD-ROM, a DVD-ROM,a Zip™ disk, a magnetic tape, or a signal encoding the process steps,and then stored in data storage device 280 in a compressed, uncompiledand/or encrypted format. In alternative embodiments, hard-wiredcircuitry may be used in place of, or in combination with,processor-executable process steps for implementation of processesaccording to embodiments of the present invention. Thus, embodiments ofthe present invention are not limited to any specific combination ofhardware and software.

Process steps of Web server 282 are also stored in data storage device280. These process steps may be executed by microprocessors 210 totransmit data to and to receive data from Web clients, such as Webbrowsers, over the Web. The data may include information from entityservers 300, 310 and 320, requests for information from user devices 400and 410, and interfaces facilitating the management of corporateentities according to some embodiments of the present invention.

Entity relationship database 283 of data storage device 280 specifiesrelationships between corporate entities managed according to thepresent embodiment. In some embodiments, the specified relationshipsindicate that a certain entity is downstream of another entity, forexample in a case that the certain entity is a subsidiary of the anotherentity. In another example, a parent company is indicated as being anupstream entity to its child companies. The information stored in entityrelationship database 283 is used in some embodiments to create aninterface including an entity selection area that allows selection of atleast one corporate entity from a plurality of corporate entities.

Data storage device 280 also stores several other databases according tosome embodiments of the present invention. Specifically, generaldatabase 284 stores information relating to the formation of a pluralityof entities, while legal database 285 includes data indicatinglegally-related information such as locations of legal documents and thelike. Contacts database 286 and owners database 287 respectively provideinformation regarding individuals having some relation to a plurality ofcorporate entities, and information identifying owners and ownershipdetails of a plurality of corporate entities. Regulators database 288identifies regulatory entities associated with corporate entities, andofficers database 289 specifies officers of corporate entities managedaccording to embodiments of the present invention.

Jurisdictions database 290 includes information related to an entity'squalifications to do business in one or more jurisdictions, andreporting database 291 specifies reporting requirements applicable toone or more of the managed entities. Controllers database 292 and fundsdatabase 293 store information respectively relating to controllers ofcorporate entities and to funds controlled by the managed corporateentities. Document generation database 294 includes information usableto automatically generate documents including information specified inone or more of databases 283 through 293. Such document generationprovides increased efficiency over previous systems for preparingdocuments that include often hard-to-retrieve information relating toseveral corporate entities.

The information stored in databases 283 through 294 may be received fromentity servers such as servers 300, 310 and 320, from an operator ofentity management server 200, or from another device. In someembodiments, the information is used to create an interface for managingcorporate entities according to embodiments of the present invention.

Also stored in data storage device 280 may also be other unshownelements that may be necessary for operation of entity management server200, such as an operating system, a database management system, otherapplications, other data files, and “device drivers” for allowingmicroprocessors 210 to interface with devices in communication withcommunication port 230. These elements are known to those skilled in theart, and are therefore not described in detail herein.

Entity Server

FIG. 3 is a block diagram of the internal components of entity server300 according to some embodiments of the invention. It should be notedthat these distinct components may comprise any of the specific examplesgiven above with respect to identically-named components of entitymanagement server 200. Of course, specific functions performed by thecomponents may differ from the functions performed by theidentically-named components.

In operation, process steps of entity management client application 392are executed by microprocessors 310 to collect and transfer informationassociated with one or more corporate entities to entity managementserver 200. As mentioned above, the information may be collected overcommunication port 330 during normal business operations and/or throughperiodic querying of departmental or company-wide data repositories incommunication with entity server 300. The information may also be inputby an operator using input device 340 and display 350. The informationis stored in entity information database 394, which may includeinformation related to one or more corporate entities.

It should be noted that entity management client application 392 mayinclude process steps usable to establish communication with andexchange data with entity management application 281. In this regard,entity server 300 may include any software and/or hardware suitable toperform the steps described herein.

User Device

FIG. 4 illustrates several components of user device 400 according tosome embodiments of the invention. Again, the illustrated components maycomprise any of the specific examples given above with respect toidentically-named components of user administration server 200 and/orentity server 300. For example, communication port 430 may be used totransmit requests for information to entity management server 200. Inthis regard, input device 440 may be used in conjunction with display450 to request and to present an interface according to some embodimentsof the invention. Input device 440, display 450 and printer 460 may alsobe used in conjunction with other applications provided by user, device400 which are unrelated to the present invention.

Storage device 490 of user device 400 stores processor-executableprocess steps of Web client 492, such as a Web browser. The processsteps may be executed by microprocessor 410 to allow communication withWeb servers such as Web server 282 of entity management server 200.Authorization information database 494 includes information that may betransmitted to entity management server 200 and used thereby todetermine whether a user of user device 400 is authorized to view someor all of an interface according to embodiments of the presentinvention.

Storage device 490 may store one or more of other applications, datafiles, device drivers and operating system files needed to providefunctions other than those directly related to the present invention.Such functions may include calendaring, e-mail access, word processing,accounting, presentation development and the like.

Databases

A tabular representation of a portion of entity relationship database283 is shown in FIG. 5. As described above, the information stored inentity relationship database 283 specifies relationships betweencorporate entities and may be used to construct an entity selection areaof an interface according to some embodiments of the present invention.Entity relationship database 293 of FIG. 5 includes several records,each consisting of several fields. The fields include entity Id field501, upstream entities field 502, and downstream entities field 503.

Entity Id field 501 includes an identifier that may be used throughoutthe databases described herein to identify a particular corporateentity. In particular, the identifier associated with a record of entityrelationship database 283 identifies a corporate entity associated withdata populating other fields of the record. The identifier may beassigned by entity management server 200 or may be received from anotherdevice.

Upstream entities field 502 includes identifiers of entities that areorganizationally upstream from the subject entity, such as a parentcompany or partial owner of the subject entity. Downstream entitiesfield 503 similarly includes identifiers of entities that areorganizationally downstream from the subject entity, such as asubsidiary or the like. As shown, a particular entity may be associatedwith multiple upstream and downstream entities.

The information stored in entity relationship database 283, as well asthat stored in each other of the databases of entity management server200, may be received from a variety of sources, including entity serverssuch as entity servers 300, 310 and 320, user devices such as userdevices 400 and 410, an operator manually inputting the informationusing input device 240, and other devices.

FIG. 6 illustrates a tabular representation of a portion of generaldatabase 284. General database 284 stores information relating to theformation of a plurality of entities. Specifically, the fields of eachrecord of database 284 include entity Id field 601, name field 602, typefield 603, status field 604, domicile field 605, taxpayer Id field 606,formed field 607, and dissolved field 608. Entity Id field 601 of arecord is used to identify an entity with which data of the record areassociated. Name field 602, type field 603, status field 604, domicilefield 605 and taxpayer Id field 606 specify respectively-namedinformation for each record. Formed field 607 and dissolved field 608indicate dates on which an associated entity was formed and dissolved,if ever.

A tabular representation of a portion of legal database 285 is shown inFIG. 7. Legal database 285 specifies legally-related information such aslocations of legal documents and the like. The records of database 285include entity id field 701, which identifies a particular corporateentity. Original minute book field 702, duplicate minute book field 703,corporate seal field 704 and stock certificate field 705 specifylocations of the original minute book, duplicate minute book, corporateseal, and stock certificate of an associated entity. Directors field 706indicates a number of directors and quorum field 707 specifies a numberof directors required for a quorum under the rules of an associatedentity.

The tabular portion of contacts database 286 illustrated in FIG. 8stores information associated with individuals having some relation to acorporate entity. In particular, for each individual reflected incontacts database 286, a record specifies an entity with which theindividual is associated in entity Id field 801, a name of theindividual in contact field 802, the individual's title in title field803, a start date associated with the individual in start date field804, an associated end date in end date. field 805, and information forcontacting the individual in contact information field 806.

FIG. 9 illustrates a tabular representation of a portion of ownersdatabase 287. As shown, owners database 287 includes informationidentifying owners and ownership details of a plurality of corporateentities. In particular, each record of owners database 287 includesentity Id field 901, owner Id field 902, type field 903, start datefield 904, end date field 905, and percent holding field 906.

Entity ID field 901 indicates an entity wholly or partially owned by anentity specified in associated owner Id field 902. Accordingly, a singleentity having multiple owners may be the subject of multiple records ofowners database 287. Type field 903 specifies the type of ownershiprelationship reflected in a record, while start date field 904 and enddate field 905 respectively specify a start date and an end date of theownership relationship. Percent holding field 906 of a record specifiesa percent of the entity identified in entity Id field 901 of the recordthat is held by the entity identified in owner Id field 902 of therecord.

FIG. 10 illustrates a tabular representation of a portion of regulatorsdatabase 288. The portion includes several records, each includingentity Id field 1001, regulator field 1002, and country/region field1003. In each record, regulator field 1002 associates a regulator with acorporate entity identified in entity Id field 1001. Country/regionfield specifies a geographical area in which the regulator possessesjurisdiction. Accordingly, regulatory requirements applicable to anentity may be determined based on the information populating regulatorsdatabase 288.

A representation of a tabular portion of officers database 289 isillustrated in FIG. 11. Each record of officers database 289 associatesinformation relating to a corporate officer with an entity of which theofficer is an officer. More particularly, each record includes entity Idfield 1101, name field 1102, title field 1103, and signatory power field1104. The latter three fields specify a name, title and signatory powerof an officer of the entity identifies by the former field.

FIG. 12 illustrates a tabular representation of a portion ofjurisdictions database 290. Jurisdictions database 290 storesinformation related to an entity's qualifications to do business in oneor more jurisdictions. Specifically, the fields of each record ofdatabase 290 include entity Id field 1201, qualified field 1202, typefield 1203, reporting field 1204, jurisdiction Id field 1205, qualifydate field 1206, and expire field 1207. Entity Id field 1201 identifiesa subject entity, while qualified field 1202 specifies a jurisdiction inwhich the entity is qualified to do business. Type field 1203 andreporting field 1204 identify the type of presence the entity has in thejurisdiction, and whether the jurisdiction requires any type ofreporting. Jurisdiction Id field 1205 includes an identifier used by thejurisdiction to identify the entity, and may comprise a taxpayeridentifier or the like. Qualify date 1206 and expire date 1207respectively indicate a date on which the entity became qualified to dobusiness in the jurisdiction, and a date on which the qualification willexpire.

A tabular representation of a portion of reporting database 291 is shownin FIG. 13. Reporting database 291 specifies information relating to thereporting requirements applicable to particular corporate entities.These requirements may be mandatory, optional, or otherwise applicable.The records of database 291 include entity id field 1301, whichidentifies a particular corporate entity. Report field 1302 specifies areport that is the subject of the record, and domicile/jurisdictionfield 1303 identifies the domicile and/or jurisdiction for which thereport is required. Due field 1304 and sent field 1305 respectivelyidentify dates on which the subject report is due and was sent. Althoughdatabase 291 as illustrated in FIG. 13 shows reports associated with asingle corporate entity, it should be noted that database 291 maydescribe reports associated with a plurality of entities.

FIG. 14 illustrates a tabular representation of a portion of controllersdatabase 292. Controllers database 292 stores information related to anentity's financial controllers. The fields of each record of database292 include entity Id field 1401, consolidation type field 1402,controllers entity type field 1403, SAO Id field 1404, SAO contactinformation field 1405, and SCRP automated flag 1406.

A tabular representation of a portion of funds database 293 is shown inFIG. 15. Funds database 293 specifies information relating to the fundsassociated with particular corporate entities. The records of database293 include entity Id field 1501, which identifies a particularcorporate entity. Trustee field 1502 names a trustee, while board noticefield 1503 and board quorum field 1504 provide information for conveningan associated board. Annuals due field 1505 specifies when annualinformation associated with the funds are due.

FIG. 16 illustrates a tabular representation of a portion of documentgeneration database 294. The portion includes several records, eachincluding document Id field 1601, document name field 1602, and documenttemplate field 1603. In each record, document name field 1602 associatesa document name with a document Id specified in document Id field 1601.Document template field 1603 specifies a location of an electronic fileincluding a document template. Accordingly, document generation database294 includes information usable to automatically generate documentsincluding information specified in one or more of databases 283 through293.

It should be noted that the illustrations and accompanying descriptionsof databases included herein merely represent relationships betweenstored information. A number of other arrangements may be employedbesides those suggested, including arrangements in which some or all ofthe specified data is located remote from the device with which it isassociated herein. It is further contemplated that each of the databasesmay include many more records than those shown and that each record mayinclude associated fields other than those illustrated.

Interface

FIG. 17 illustrates an outward view of user interface 1700 as presentedby display 450 of user device 400. According to some embodiments, a useroperates input device 440 of user device 400 to input a Uniform ResourceLocator (URL) into address bar 1710 of a window presented according toprocess steps of Web client 492. The process steps are executed totransmit a request for a Web page corresponding to the URL to Web server282 of entity management server 200, and to receive the Web pagetherefrom.

In the present example, interface 1700 is the Web page received fromentity management server 200. Interface 1700 includes input area 1720for receiving logon information from the user, and Submit button 1730for submitting the logon information to entity management server 200.Upon receiving the logon information, entity management application 281determines whether the user is authorized to access interfaces accordingto some embodiments of the present invention. In this regard,authorization information 494 may also or alternatively be submitted todetermine a user's authorization.

If the user is authorized to view information provided by the presentexample, entity selection interface 1800 is presented to user device 400and in turn presented to the user via display 450. Interface 1800includes instructions 1810, interface links 1815 and entity selectionarea 1820. Instructions 1810 instruct the user to select an entity fromentity selection area 1820 and to select one of links 1815 to viewcorresponding information relating to the selected entity. As shown, theentities presented in entity selection area 1820 are associated with anicon indicating that downstream entities are associated with eachentity. In this regard, information stored in entity relationshipdatabase may be used to construct selection area 1820.

FIG. 19 illustrates user interface 1900, which is presented after theuser selects the icons associated with the entities of entity selectionarea 1820, selects an entity from the resulting expanded tree structure,and selects the General link of links 1815. The expanded tree structureis shown in entity selection area 1910, and conforms to the informationstored in entity relationship database 283. Main area 1920 presentsinformation associated with the selected entity in general database 284.The user may select another entity from entity selection area 1910 toview information associated with the another entity in database 284, ormay select another link to view other information associated with theoriginally-selected entity.

Interface 2000 is presented upon selection of the Legal link. Main area2010 of interface 2000 presents information that is associated with theselected entity in legal database 285. Similarly, FIG. 21 shows thatmain area 2110 of interface 2100 presents contact information associatedwith the selected entity in contacts database 296. As also shown,contact names 2120 comprise hyperlinks that may be selected to viewcontact information associated with each contact name in database 296.

FIG. 22 illustrates interface 2200 as presented upon selection of theOwners link. Area 2210 of interface 2200 presents information associatedwith the selected entity in owners database 287. Like area 2110, area2210 includes hyperlinks 2220 that may be selected to view informationassociated with the presented owners. Regulators interface 2300 of FIG.23 presents, in area 2310, information stored in regulators database 288that is associated with the selected entity in regulators database 288.

Information associated with the selected entity in officers database 289is presented through user interface 2400 of FIG. 24. More specifically,area 2410 presents names, titles, and descriptions of signatory powerfor entity directors. Each name comprises a hyperlink that is selectableto view further information associated with the named officer. FIG. 25shows the information of jurisdictions database 290 as reflected in area2510 of interface 2500. Accordingly, interface 2500 is presented inresponse to user selection of the Jurisdictions link.

Selection of the Reporting link causes presentation of interface 2600.As shown in FIG. 26, area 2610 of interface 2600 presents informationassociated with the selected entity in reporting database 291. FIG. 27shows interface 2700, which is presented in response to selection of theControllers link. Area 2710 of interface 2700 presents informationstored in controllers database 292. Similarly, FIG. 28 shows interface2800 and area 2810, which are presented in response to selection of theFunds link. Accordingly, area 2810 presents information stored in fundsdatabase 293.

FIG. 29 shows display 450 presenting interface 2900. Interface 2900 ispresented in response to user selection of the Maintenance link from anyof the interfaces of FIGS. 18 through 28. Interface 2900 includes menu2910 of Tools and Maintenance options. Any of these options may beselected in order to perform the task specified by the selected option.According to FIG. 29, the New Entity option has been selected andtherefore main area 2920 includes an interface for defining a newentity.

Interface 3000 of FIG. 30 is presented in response to user selection ofthe Document Generation option from menu 2910. Interface 3000 may beused to generate documents relating to one or more corporate entities.According to the illustrated embodiment, an entity and a document areselected using pull-down menus located in main area 3010. In thisregard, the pull-down menus may be populated, respectively, byinformation stored in general database 284 and document generationdatabase 294.

By virtue of one or more of the foregoing features, some embodiments ofthe present invention provide an efficient interface for management ofinformation related to corporate entities. It should be noted that theuser interfaces of FIGS. 17 through 30 may be considered a single userinterface. Moreover, a user interface according to embodiments of thepresent invention may be arranged differently than as shown, with all orsome of the features of user interfaces 1700 through 3000 located withinone or more user interfaces.

One or more of the interfaces described herein may include areas thatallow editing of the information presented therein. Editing may beallowed based on editing rights of a user to whom the interface ispresented, with several editing authority levels being available. Insome embodiments, such editing causes editing of correspondinginformation stored in one or more of databases 283 through 294. Also insome embodiments, edited information may be associated with informationindicating who edited the information and a date on which theinformation was edited. Furthermore, an interface according to someembodiments of the invention may present indications to a user thatinformation presented therein is in the process of being edited byanother user.

As mentioned above, each of databases 283 through 294 may containinformation other than that explicitly mentioned herein. Accordingly,each of interfaces 1700 through 3000 may also present information otherthan that described herein. In one example, one or more of theinterfaces may include links selectable to cause presentation of an areapresenting images of documents relating to the at least one corporateentity. In another example, officers database 289 and interface 2400track outside directorships held by each presented officer. Thedatabases and interfaces related to reporting requirements may alsoprovide a filing calendar that may be searched or organized by factorssuch as due date, entity, responsible division, responsible person, andregulatory body.

In some embodiments, entity management server 200 may be integrated withother devices operated by an entity maintaining server 200. In addition,many of the embodiments described herein are directed to the financialservices and securities-related entities. However, embodiments of thepresent invention are applicable to many types of entities that arerelated to many types of businesses.

The present invention has been described in terms of several embodimentssolely for the purpose of illustration. Persons skilled in the art willrecognize from this description that the invention is not limited to theembodiments described, but may be practiced with modifications andalterations limited only by the spirit and scope of the appended claims.

1-31. (canceled)
 32. A processor-implemented method comprising:generating a user interface including a plurality of user selectablecorporate entities; receiving a user selection of a corporate entity viathe user interface; retrieving via a processor, corporate information ofthe corporate entity, wherein the corporate information includes atleast ownership information; determining a plurality of corporateentities having ownership relationships with the user selected corporateentity based on the retrieved corporate information; presenting, basedon the retrieved corporate information, a tiered selectable corporateownership structure including the determined plurality of corporateentities showing ownership relationships and a user selectable corporateinformation category tab, wherein a first one of the plurality ofcorporate entities is at least a partial owner of a second one of theplurality of corporate entities; receiving a selection of the secondcorporate entity; receiving a selection of the user selectable corporateinformation category tab; retrieving a category of corporate informationcorresponding to the selected corporate information category tab anddetermining at least a portion of the retrieved category of corporateinformation to be related to the second corporate entity; and presentingthe determined information to a user.
 33. A method according to claim32, wherein the determined information comprises one or more of:information relating to a formation of the second corporate entity; alocation of corporate documents relating to the second corporate entity;contact information relating to the second corporate entity; ownershipinformation relating to the second corporate entity; informationrelating to regulators of the second corporate entity; informationrelating to officers of the second corporate entity; informationrelating to jurisdictions in which the second corporate entity isqualified to do business; information relating to reports filed or to befiled on behalf of the second corporate entity; controllers informationrelating to the second corporate entity; and funds information relatingto the second corporate entity.
 34. A method according to claim 32,further comprising: receiving instructions to generate a documentincluding document information relating to the second corporate entity;determining the document information; generating the document; andpresenting the document to the user.
 35. A method according to claim 32,further comprising: receiving instructions to edit the determinedinformation; determining whether the user is authorized to edit thedetermined information; and editing the determined information if it isdetermined that the user is authorized to edit the determinedinformation.
 36. A method according to claim 35, further comprising:associating information identifying the user with the editedinformation.
 37. A method according to claim 35, further comprising:presenting an indication that the determined information is in theprocess of being edited.
 38. A method according to claim 32, furthercomprising: associating information identifying a date on which theinformation was edited with the edited information.
 39. A methodaccording to claim 32, further comprising: receiving a request for animage of a document relating to the selected second corporate entity;and presenting the image to the user.
 40. A computer-readable mediumstoring processor executable instructions comprising instructions to:generate a user interface including a plurality of user selectablecorporate entities; receive a user selection of a corporate entity viathe user interface; retrieve via a processor, corporate information ofthe corporate entity, wherein the corporate information includes atleast ownership information; determine a plurality of corporate entitieshaving ownership relationships with the user selected corporate entitybased on the retrieved corporate information; present, based on theretrieved corporate information, a tiered selectable corporate ownershipstructure including the determined plurality of corporate entitiesshowing ownership relationships and a user selectable corporateinformation category tab, wherein a first one of the plurality ofcorporate entities is at least a partial owner of a second one of theplurality of corporate entities; receive a selection of the secondcorporate entity; receive a selection of the user selectable corporateinformation category tab; retrieve a category of corporate informationcorresponding to the selected corporate information category tab anddetermining at least a portion of the retrieved information to berelated to relating to the second corporate entity; and present thedetermined information to a user.
 41. A computer-readable mediumaccording to claim 40, wherein the determined information comprises oneor more of: information relating to a formation of the second corporateentity; a location of corporate documents relating to the secondcorporate entity; contact information relating to the second corporateentity; ownership information relating to the second corporate entity;information relating to regulators of the second corporate entity;information relating to officers of the second corporate entity;information relating to jurisdictions in which the second corporateentity is qualified to do business; information relating to reportsfiled or to be filed on behalf of the second corporate entity;controllers information relating to the second corporate entity; andfunds information relating to the second corporate entity.
 42. Acomputer-readable medium according to claim 40, further comprisinginstructions to: receive instructions to generate a document includingdocument information relating to the second corporate entity; determinethe document information; generate the document; and present thedocument to the user.
 43. A computer-readable medium according to claim40, further comprising instructions to: receive instructions to edit thedetermined information; determine whether the user is authorized to editthe determined information; and edit the determined information if it isdetermined that the user is authorized to edit the determinedinformation.
 44. A computer-readable medium according to claim 43,further comprising instructions to: associate information identifyingthe user with the edited information.
 45. A computer-readable mediumaccording to claim 43, further comprising instructions to: present anindication that the determined information is in the process of beingedited.
 46. A computer-readable medium according to claim 40, theprocess steps further comprising instructions to: associate informationidentifying a date on which the information was the edited information.47. A computer-readable medium according to claim 40, the process stepsfurther comprising instructions to: receive a request for an image of adocument relating to the second corporate entity; and present the imageto the user.
 48. An apparatus to manage corporate entities, comprising:a processor; and a storage device in communication with said processorand storing instructions adapted to be executed by said processor to:generate a user interface including a plurality of user selectablecorporate entities; receive a user selection of a corporate entity viathe user interface; retrieve via a processor, corporate information ofthe corporate entity, wherein the corporate information includes atleast ownership information; determine a plurality of corporate entitieshaving ownership relationships with the user selected corporate entitybased on the retrieved corporate information; present, based on theretrieved corporate information, a tiered selectable corporate ownershipstructure including the determined plurality of corporate entitiesshowing ownership relationships and a user selectable corporateinformation category tab, wherein a first one of the plurality ofcorporate entities is at least a partial owner of a second one of theplurality of corporate; receive a selection of the second corporateentity; receive a selection of the user selectable corporate informationcategory tab; retrieve a category of corporate information correspondingto the selected corporate information category tab and determining atleast a portion of the retrieved information to be related to relatingto the second corporate entity; and present the determined informationto a user.
 49. An apparatus according to claim 48, wherein thedetermined information comprises one or more of: information relating toa formation of the second corporate entity; a location of corporatedocuments relating to the second corporate entity; contact informationrelating to the second corporate entity; ownership information relatingto the second corporate entity; information relating to regulators ofthe second corporate entity; information relating to officers of thesecond corporate entity; information relating to jurisdictions in whichthe second corporate entity is qualified to do business; informationrelating to reports filed or to be filed on behalf of the secondcorporate entity; controllers information relating to the secondcorporate entity; and funds information relating to the second corporateentity.
 50. An apparatus according to claim 48, the instructions furtheradapted to be executed by said processor to: receive instructions togenerate a document including document information relating to thesecond corporate entity; determine the document information; generatethe document; and present the document to the user.
 51. An apparatusaccording to claim 48, the instructions further adapted to be executedby said processor to: receive instructions to edit the determinedinformation; determine whether the user is authorized to edit thedetermined information; and edit the determined information if it isdetermined that the user is authorized to edit the determinedinformation.
 52. An apparatus according to claim 51, the instructionsfurther adapted to be executed by said processor to: associateinformation identifying the user with the edited information.
 53. Anapparatus according to claim 51, the instructions further adapted to beexecuted by said processor to: present an indication that the determinedinformation is in the process of being edited.
 54. An apparatusaccording to claim 48, the instructions further adapted to be executedby said processor to: receive a request for an image of a documentrelating to the second corporate entity; and present the image to theuser.